Conversation
|
This PR will trigger no release when merged. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
@solaris007 Appreciate checking the IPs and adding both variables to secrets manager on all 3 environments. Review comments are addressed.
|
|
@solaris007 what could be causing this deploy error? Changes made should not effect deployment in my view.
|
|
@solaris007 I noticed on aws console lambda is being deployed. For some reason Jenkins deployer is showing the error I shared earlier. |
solaris007
left a comment
There was a problem hiding this comment.
Re-review - All requested changes addressed
The 4 issues from the previous review have all been fixed:
- Mock paths now correctly target
bot-detection.js(verified all esmock calls) - Dead re-export removed -
cloudwatch-utils.jsonly exportsgetAuditStatus sortJobsByDatefunction vssortedJobsresult - no more name collision- Single
bot-detection.test.js, no duplicate test file
Bot detection end-to-end flow is clean: handler gets jobId from scrape jobs, checkAndAlertBotProtection reads abortInfo via ScrapeClient, converts to stats, sends Slack alert. LGTM.
Minor cleanup items
-
Duplicate JSDoc on
filterJobsByTimestamp- Two JSDoc blocks stacked on the same function. Remove the shorter one. -
Unnecessary esmock mock -
bot-detection.test.jsmocksfetchRecentThreadMessagesfromslack-utils.js, butbot-detection.jsdoesn't import it. Harmless but confusing. -
Gist tarball dependencies - 4 packages on gist tarballs. Must be replaced with published npm versions once #1308 merges.
-
getScrapeJobsByBaseURLno longer filters by'default'processing type - Intentional? This now returns jobs of all processing types. Just confirming this is desired behavior.
|
@solaris007 addressed your comments. For some reason this PR is not getting deployed. When I created fresh test PR it deployed fine. When I created new PR out of this PR it failed. That means some state in this PR is causing issue. I am running out of ideas. One other option is just cherry pick code to new PR. This issue started happening only from yesterday. Update: Upgrading to latest @adobe/helix-deploy (same as in audit worker) solved the issue. |
# [1.9.0](v1.8.2...v1.9.0) (2026-02-13) ### Features * bot detection logic ([#170](#170)) ([1741930](1741930))
|
🎉 This PR is included in version 1.9.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |

Implemented comprehensive bot protection detection and alerting in the Task Processor to identify when sites are blocked by bot protection services (Cloudflare, Akamai, Imperva, etc.) and prevent unnecessary processing.
Tests:
DynamoDB records created and fetched using scrape client:
Sample record
Debug Log:
Tests:
https://cq-dev.slack.com/archives/C060T2PPF8V/p1770848981948789?thread_ts=1770846988.025919&cid=C060T2PPF8V